-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: mcp-bridge flaky test #12863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
fix: mcp-bridge flaky test #12863
Conversation
|
@LiteSun still one test case failed, pls fix it |
done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have already extracted and copied package-lock.json from the archive package. Does this still need to be committed separately?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have already extracted and copied package-lock.json from the archive package. Does this still need to be committed separately?
Good catch. I didn’t notice before that there was already a lock file at the npm workspace level. It has been updated.
membphis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ci/prepare_filesystem_mcp.sh
Outdated
| ( | ||
| cd "${DEST_DIR}" | ||
| npm install | ||
| # Note: Although dlx specifies the package version, it does not use a lockfile, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, it is really important and useful information
Background
In previous tests, the MCP Server was started using the following command:
However, during repeated test runs, this approach was found to cause unstable sub-dependency resolution. Different runs could resolve different versions of transitive dependencies, leading to MCP Server startup failures or inconsistent behavior, which negatively impacted test reliability.
Changes
To ensure stability and reproducibility of the test environment, this PR updates the build process for
[email protected]as follows:pnpm dlxto dynamically fetch and execute the packagehttps://github.com/modelcontextprotocol/servers/archive/refs/tags/2025.7.1.tar.gz[email protected]MCP Server using the includedpackage-lock.jsonScope of Impact
[email protected])Checklist